Skip to main content

This is a new service – your feedback will help us to improve it.

Bristol City Council

Tree preservation zone

There is a problem

  • 365 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

Hiatt Baker Hall Parrys Lane Bristol BS9 1AD

reference
LSWLRHDN0BB00
name
Hiatt Baker Hall Parrys Lane Bristol BS9 1AD
tree-preservation-order

undefined

299
tree-preservation-zone-type
group
geometry
MULTIPOLYGON (((-2.623886 51.481258,-2.623872 51.481278,-2.623892 51.481319,-2.623910 51.481338,-2.624204 51.481537,-2.624227 51.481547,-2.624356 51.481555,-2.624383 51.481536,-2.624378 51.481499,-2.624342 51.481439,-2.624271 51.481371,-2.624149 51.481280,-2.624081 51.481263,-2.623886 51.481258)),((-2.624414 51.481537,-2.624356 51.481556,-2.624325 51.481615,-2.624413 51.481634,-2.624479 51.481621,-2.624496 51.481589,-2.624486 51.481555,-2.624451 51.481539,-2.624414 51.481537)),((-2.623817 51.481095,-2.623780 51.481113,-2.623758 51.481150,-2.623762 51.481177,-2.623783 51.481202,-2.623856 51.481218,-2.623887 51.481212,-2.623942 51.481184,-2.623958 51.481141,-2.623914 51.481103,-2.623887 51.481089,-2.623817 51.481095)),((-2.623733 51.481016,-2.623692 51.481025,-2.623631 51.480993,-2.623583 51.481000,-2.623545 51.481032,-2.623537 51.481060,-2.623551 51.481090,-2.623569 51.481109,-2.623583 51.481112,-2.623643 51.481112,-2.623762 51.481094,-2.623785 51.481076,-2.623787 51.481065,-2.623773 51.481024,-2.623733 51.481016)))
point
POINT (-2.624045 51.481322)
notes
COMMON, LONG LEAVED AND SMALL LEAVED LIME
organisation
entry-date
2011-10-11
start-date
2011-10-11
end-date

How to fix this issue

Your dataset is missing the tree-preservation-order column.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Bristol City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL